Instantiation and management of physical and virtualized network functions of a radio access network node

ABSTRACT

A network management function (NMF) is configured to instantiate a network service (NS), update a NS, and/or establish a relation between a virtualized network function (VNF) instance and a physical network function (PNF) instance. The NMF may instantiate, for example, a NS including a new VNF that is part of a base station or a g Node B (gNB), a NS including a PNF that is part of the gNB, or a NS that includes a PNF and a new VNF that form a gNB. The NMF may also, for example, update a NS to add a VNF instance to a NS that already includes a PNF instance to form a gNB, or update a NS to add a PNF instance to a NS that already includes a VNF instance to form a gNB.

RELATED APPLICATIONS

This application claims the benefit under 35 U.S.C. § 119(e) of U.S.Provisional Patent Application No. 62/442,876, filed Jan. 5, 2017, whichis hereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

Various embodiments may relate to the field of wireless communications.More particularly, this disclosure is directed to virtualized networkfunctions that are part of a radio access network.

BACKGROUND

Wireless mobile communication technology uses various standards andprotocols to transmit data between a base station and a wireless mobiledevice. Wireless communication system standards and protocols caninclude the 3rd Generation Partnership Project (3GPP) long termevolution (LTE); the Institute of Electrical and Electronics Engineers(IEEE) 802.16 standard, which is commonly known to industry groups asworldwide interoperability for microwave access (WiMAX); and the IEEE802.11 standard for wireless local area networks (WLAN), which iscommonly known to industry groups as Wi-Fi. In 3GPP radio accessnetworks (RANs) in LTE systems, the base station (BS) can include a RANNode such as a Evolved Universal Terrestrial Radio Access Network(E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced NodeB, eNodeB, or eNB) and/or Radio Network Controller (RNC) in an E-UTRAN,which communicate with a wireless communication device, known as userequipment (UE). In fifth generation (5G) or next generation (NG)wireless RANs, RAN Nodes, named as NG-RAN nodes, can include a 5G Node,new radio (NR) node or NR BS, or g Node B (gNB).

RANs use a radio access technology (RAT) to communicate between the RANNode and UE. RANs can include global system for mobile communications(GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN),Universal Terrestrial Radio Access Network (UTRAN), and/or E-UTRAN,which provide access to communication services through a core network.Each of the RANs operates according to a specific 3GPP RAT. For example,the GERAN implements GSM and/or EDGE RAT, the UTRAN implements universalmobile telecommunication system (UMTS) RAT or other 3GPP RAT, and theE-UTRAN implements LTE RAT.

A core network can be connected to the UE through the RAN Node. The corenetwork can include a serving gateway (SGW), a packet data network (PDN)gateway (PGW), an access network detection and selection function(ANDSF) server, an enhanced packet data gateway (ePDG) and/or a mobilitymanagement entity (MME).

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B are block diagrams illustrating new radio access networkarchitectures with a functional split between upper layers and lowerlayers of NR stacks according to certain embodiments.

FIG. 2A is a diagram illustrating a network management architecture formobile networks that include virtualized network functions which can bepart of EPC or IMS according to certain embodiments.

FIG. 2B is a diagram illustrating an example network managementarchitecture for 5G networks that include virtualized network functionsthat can be part of 5GC and NG-RAN according to certain embodiments.

FIG. 3 is a flow chart of a method to instantiate a network service (NS)according to certain embodiments.

FIG. 4 is a flow chart of a method to update a NS according to certainembodiments.

FIG. 5 is a flow chart of a method to establish a relation between anetwork function instance that is virtualized and a network functioninstance that is non-virtualized forming a gNB according to certainembodiments.

FIG. 6 illustrates an architecture of a system of a network inaccordance with some embodiments.

FIG. 7 illustrates example components of a device in accordance withsome embodiments.

FIG. 8 illustrates example interfaces of baseband circuitry inaccordance with some embodiments.

FIG. 9 illustrates components of a core network in accordance with someembodiments.

FIG. 10 is a block diagram illustrating components, according to someexample embodiments, able to read instructions from a machine-readableor computer-readable and perform any one or more of the methodologiesdiscussed herein.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

A detailed description of systems and methods consistent withembodiments of the present disclosure is provided below. While severalembodiments are described, it should be understood that the disclosureis not limited to any one embodiment, but instead encompasses numerousalternatives, modifications, and equivalents. In addition, whilenumerous specific details are set forth in the following description inorder to provide a thorough understanding of the embodiments disclosedherein, some embodiments can be practiced without some or all of thesedetails. Moreover, for the purpose of clarity, certain technicalmaterial that is known in the related art has not been described indetail in order to avoid unnecessarily obscuring the disclosure.

Embodiments disclosed herein are directed to management aspects ofvirtualized network functions (VNFs), and certain examples are providedfor the management of VNFs that are part of new radio access networks(e.g., 5G). Skilled persons will recognize from the disclosure herein,however, that certain embodiments may be applicable to both gNB andother types of RAN nodes.

Certain NR BS deployments use a function split feature that splits a gNBinto one or more centralized unit (CU) (upper layer of NR BS) and one ormore distributed unit (DU) (lower layer NR BS). NR allows CU deploymentwith network function virtualization (NFV). Thus, for example, a gNB maycomprise a CU that is implemented as VNF running in the cloud and a DUrunning in a cell site that provides wireless communication to a UE.

A CU may be connected to one or more DU. A DU may be connected to one ormore CU. For example, FIGS. 1A and 1B are block diagrams illustratingnew radio access network architectures that include upper layers andlower layers of NR stacks according to certain embodiments. In theexample shown in FIG. 1A, a first CU 102 and a second CU 104 are part ofa first NR BS 100 (e.g., gNB) that includes a DU 108. In the exampleshown in FIG. 1B, a first DU 110 and a second DU 112 are part of asecond NR BS 101 (e.g., gNB) that includes a CU 106. In both examples,the CUs 102, 104, 106 are implemented as VNF (e.g., running in thecloud) and the DUs 108, 110, 112 run in a respective cell site thatprovides wireless communication to UEs.

The functional split between the CU and DU of gNB nodes may depend onthe transport layer. High performance transport between the CU and DU ofgNB nodes, e.g., optical networks, can enable advanced coordinatedmulti-point (CoMP) schemes and scheduling optimization, which could beuseful in high capacity scenarios, or scenarios where cross cellcoordination is beneficial. Low performance transport between the CU andBU of gNB nodes can enable the higher protocol layers of the NR radiostacks to be supported in the CU, since the higher protocol layers havelower performance requirements on the transport layer in terms ofbandwidth, delay, synchronization and jitter.

Certain embodiments herein relate to life cycle management functions toinstantiate a network service (NS) to include VNF and physical networkfunction (PNF) that form a gNB.

In an example embodiment, an apparatus includes an NR RAN node or gNBincluding a CU (i.e., upper layer of NR BS) that may be implemented asVNF deployed in the cloud, and a DU (i.e., lower layer of NR BS) thatmay be implemented as vertical hardware deployed in a cell site toprovide wireless communication to UE. In certain such embodiments, a gNBmay include a CU connected to one or more DUs. In addition, or in otherembodiments, a gNB may include a DU connected to one or more CUs.

In another example embodiment, a network management function (NMF) thatmay be supported by one or more processors to send a request to an NFVorchestrator (NFVO) to create a new NS identifier, receive from NFVO thenew NS identifier, send a request to the NFVO to instantiate a NS thatincludes the instantiation of a new VNF to implement a CU that is partof a gNB, send a request to the NFVO to instantiate a NS that includes aPNF to implement a DU that is part of the gNB, send a request to NFVO toinstantiate a NS that includes the instantiation of a new VNF andaddition of a PNF to form the gNB, receive from the NFVO the operationresult including the lifecycle operation occurrence identifier, receivefrom the NFVO the NS lifecycle change notification to the NMF indicatingthe start of NS instantiation, and receive from the NFVO a NS lifecyclechange notification to the NMF indicating the result of the NSinstantiation. In certain such embodiments, the request to instantiate aNS that includes the instantiation of a new VNF contains attributes(e.g., additionalParamForVnf) to provide additional parameter(s) per VNFinstance that are used for VNF instantiation. The request to instantiatea NS that contains a PNF may also include attributes (e.g., pnflnfo) toprovide the information of PNF to be added to the NS instance.

In another example embodiment, an NMF that may be supported by one ormore processors to send a request to an NFVO to update a NS to add a VNFinstance, send a request to the NFVO to update a NS to add a PNFinstance, receive from the NFVO the operation result including thelifecycle operation occurrence identifier, receive from the NFVO the NSlifecycle change notification to the NMF indicating the start of NSupdate, and receive from the NFVO the NS lifecycle change notificationto the NMF indicating the result of NS update. In certain suchembodiment, the request to update a NS that adds a VNF instance includesattributes 1) nslnstanceld that identifies the NS instance where the VNFinstance is to be added, and 2) addVnflnstance that provides theexisting instance to be added to the NS instance. In certainembodiments, the request to update a NS that adds a PNF instance mayinclude attributes 1) nslnstanceld that identifies the NS instance wherethe VNF instance is to be added, and 2) pnflnfo that provides theinformation of PNF to be added to the NS instance.

In another example embodiment, an NMF that may be supported by one ormore processors to send a request to an network function managementfunction (NFMF) to establish a relation between network functioninstances that are virtualized and network function instances that arenon-virtualized, receive a response from the NFMF indicating that therelation between network function instances that are virtualized andnetwork function instances that are non-virtualized has beenestablished, and/or receive a response from the NFMF indicating that therelation of network function instance that is virtualized and networkfunction that is non-virtualizesd cannot be established. In certain suchembodiments, the VNF instance has been instantiated, and a managedobject instance (MOI) representing the network function instance that isvirtualized has been created. The PNF instance may be deployed and theMOI representing the network function instance that is non-virtualizedmay have been created. In certain embodiments, the relation betweennetwork function instance that is virtualized and network functioninstance that is non-virtualized indicates that the network functioninstance that is virtualized and network function instance that isnon-virtualized are used to form a gNB. One network function instancethat is virtualized may have relations with one or more network functioninstances that are non-virtualized. Alternatively, one network functioninstance that is non-virtualized may have relations with one or morenetwork function instances that are virtualized. In certain embodiments,the NMF knows which network function instance that is virtualized andnetwork function instance that is non-virtualized can be used to form agNB such that the relation between them can be established. In certainembodiments, the NFMF validates the relation between network functioninstance that is virtualized and network function instance that isnon-virtualized. If the relation is valid, the NFMF is to configure thenetwork function instance that is virtualized and network functioninstance that is non-virtualized to establish the relation, and send aresponse to the NMF indicating the relation has been established. If therelation is invalid, on the other hand, the NFMF is to send a responseto the NMF indicating the relation cannot be established.

Certain embodiments include an apparatus comprising means to perform oneor more elements of a method described in or related to any of theexamples described herein.

Certain embodiments include one or more non-transitory computer-readablemedia comprising instructions to cause an electronic device, uponexecution of the instructions by one or more processors of theelectronic device, to perform one or more elements of a method describedin or related to any of the examples described herein.

Certain embodiments include an apparatus comprising logic, modules,and/or circuitry to perform one or more elements of a method describedin or related to any of the examples described herein.

Certain embodiments include a method, technique, or process as describedin or related to any of the examples, or portions or parts thereof.

Certain embodiments include an apparatus comprising one or moreprocessors and one or more computer readable media comprisinginstructions that, when executed by the one or more processors, causethe one or more processors to perform the method, techniques, or processas described in or related to any of examples, or portions thereof.

Certain embodiments include a method of communicating in a wirelessnetwork as shown and described herein.

Certain embodiments include a system for providing wirelesscommunication as shown and described herein.

Certain embodiments include a device for providing wirelesscommunication as shown and described herein.

In some embodiments, virtualized can be spelled as virtualised herein,however the meaning is the same.

NFV architectures and infrastructures may be used to virtualize one ormore network functions, alternatively performed by proprietary hardware,onto physical resources comprising a combination of industry-standardserver hardware, storage hardware, or switches. In other words, NFVsystems can be used to execute virtual or reconfigurable implementationsof one or more EPC components/functions.

FIG. 2A is a diagram illustrating a network management architecture 200for mobile networks that include virtualized network functions (VNFs ornetwork function virtualization (NFV) more generally) which can be partof EPC and IMS. The illustrated network management architecture 200 isprovided by way of example only and skilled persons will recognize fromthe disclosure herein that the described embodiments may also be usedwith other virtualized network architectures. The components shown inFIG. 2A, according to some example embodiments, can support NFV. Thesystem 200 is illustrated as including a virtualized infrastructuremanager (VIM) 202, a network function virtualization infrastructure(NFVI) 204, a VNF manager (VNFM) 206, virtualized network functions(VNFs) 208, an element manager (EM) 210, an NFV orchestrator (NFVO) 212,and a network manager (NM) 214 within an operation supportsystem/business support system (OSS/BSS) 222.

The VIM 202 manages the resources of the NFVI 204. The NFVI 204 caninclude physical or virtual resources and applications (includinghypervisors) used to execute the system 200. The VIM 202 may manage thelife cycle of virtual resources with the NFVI 204 (e.g., creation,maintenance, and tear down of virtual machines (VMs) associated with oneor more physical resources), track VM instances, track performance,fault and security of VM instances and associated physical resources,and expose VM instances and associated physical resources to othermanagement systems.

The VNFM 206 may manage the VNFs 208. The VNFs 208 may be used toexecute IP multimedia subsystem (IMS), evolved packet core (EPC) and 5G(5GC and NG-RAN) components/functions. The VNFM 206 may manage the lifecycle of the VNFs 208 and track performance, fault and security of thevirtual aspects of VNFs 208. The EM 210 may track the performance, faultand security of the functional aspects of VNFs 208 and physical networkfunctions (PNFs) 224. The tracking data from the VNFM 206 and the EM 210may comprise, for example, performance measurement (PM) data used by theVIM 202 or the NFVI 204. Both the VNFM 206 and the EM 210 can scaleup/down the quantity of VNFs 208 of the system 200. In some embodiments,the EM 210 is responsible for fault, configuration, accounting,performance and security management (FCAPS). In other embodiments, theEM 210 can manage multiple VNFs 208 or multiple EMs 210 manage a singleVNF 208 each. In an embodiment, the EM 210 can be a VNF 208 itself. Inan embodiment, the combination of the NM 214, a domain manager (DM) 226and/or the EM 210 is considered to be a third generation partnershipproject (3GPP) management system.

The NFVO 212 may coordinate, authorize, release and engage resources ofthe NFVI 204 in order to provide the requested network service (e.g.,which may be used to execute an EPC function, component, or slice). TheNM 214 may provide a package of end-user functions with theresponsibility for the management of a network, which may includenetwork elements with VNFs 208, non-virtualized network functions, orboth (management of the VNFs 208 may occur via the EM 210). The OSSportion of the OSS/BSS 222 is responsible for network management, faultmanagement, configuration management and service management. The BSSportion of the OSS/BSS 222 is responsible for customer management,product management and order management. In the NFV architecture, thecurrent BSS/OSS 222 of an operator may be interworking with an NFVmanagement and orchestration (NFV-MANO) 232 using standard interfaces(or reference points).

Interconnection points (or reference points) between functional blockscan expose an external view of a functional block. These can includeOS-Ma-nfvo between the NM 214 and NFVO 212; Ve-VNFM-em between the EM210 and the VNFM 206; Ve-Vnfm-vnf between a VNF 208 and VNFM 206;Or-Vnfm between the NFVO 212 and the VNFM 206; Or-Vi between the NFVO212 and the VIM 202; Vi-Vnfm between the VNFM 206 and VIM 202; NF-Vibetween the NFVI 204 and the VIM 202; VN-Nf between the NFVI 204 and VNF208; and Itf-N between the EM 210 or DM 226 and NM 214.

A virtualized resource performance management interface has been definedfor reference point Vi-Vnfm between VIM 202 and VNFM 206 as shown inFIG. 2A. The operations to create a PM job and notify the availabilityof PM data can be transmitted using the above-mentioned interface. Theusage of an individual virtual CPU (sometimes called a virtual processoror vCPU) is a part of a virtualized resource (VR), or the consolidatedusage of all virtual CPUs of a Virtualized Compute Resource and can bemonitored by a performance measurement.

The example network architecture shown in FIG. 2A may be for 4G/LTEnetworks. However, certain embodiments herein may also be applicable to5G networks. Thus, FIG. 2B is a diagram illustrating an example networkmanagement architecture 201 for 5G networks that include virtualizednetwork functions that can be part of 5GC and NG-RAN according tocertain embodiments. The illustrated network management architecture 201is provided by way of example only and skilled persons will recognizefrom the disclosure herein that the described embodiments may also beused with other virtualized network architectures. The components shownin FIG. 2B, according to some example embodiments, can support NFV. Thesystem 201 is illustrated as including a virtualized infrastructuremanager (VIM) 202, a network function virtualization infrastructure(NFVI) 204, a VNF manager (VNFM) 206, virtualized network functions(VNFs) 208, an network function management function (NFMF) 260, an NFVorchestrator (NFVO) 212, and a network management function (NMF) 250within an operation support system/business support system (OSS/BSS)222. In certain embodiments, the NMF 250 may be located in a NM and theNFMF 260 may be located in an EM or DM, such as the NM 214, the EM 210,or the DM 226 shown in FIG. 2A.

The VIM 202 manages the resources of the NFVI 204. The NFVI 204 caninclude physical or virtual resources and applications (includinghypervisors) used to execute the system 201. The VIM 202 may manage thelife cycle of virtual resources with the NFVI 204 (e.g., creation,maintenance, and tear down of virtual machines (VMs) associated with oneor more physical resources), track VM instances, track performance,fault and security of VM instances and associated physical resources,and expose VM instances and associated physical resources to othermanagement systems.

The VNFM 206 may manage the VNFs 208. The VNFs 208 may be used toexecute IMS, EPC and 5G (5GC and NG-RAN) components/functions. The VNFM206 may manage the life cycle of the VNFs 208 and track performance,fault and security of the virtual aspects of VNFs 208. The NFMF 260 maytrack the performance, fault and security of the functional aspects ofVNFs 208 and physical network functions (PNFs) 224. The tracking datafrom the VNFM 206 and the NFMF 260 may comprise, for example,performance measurement (PM) data used by the VIM 202 or the NFVI 204.Both the VNFM 206 and the NFMF 260 can scale up/down the quantity ofVNFs 208 of the system 201. In some embodiments, the NFMF 260 isresponsible for fault, configuration, accounting, performance andsecurity management (FCAPS). In other embodiments, the NFMF 260 canmanage multiple VNFs 208 or multiple NFMFs 260 manage a single VNF 208each. In an embodiment, the NFMF 260 can be a VNF 208 itself. In thisexample embodiment, the combination of the NMF 250 and the NFMF 260 isconsidered to be a 3GPP management system 232. Thus, unlike the 3GPPmanagement system 230 shown in FIG. 2A that includes management entitieslike the NM 214 and the EM 210, the 3GPP management system 232 of thisexample for 5G networks only includes logical management functions.

The NFVO 212 may coordinate, authorize, release and engage resources ofthe NFVI 204 in order to provide the requested network service (e.g.,which may be used to execute an EPC function, component, or slice). TheNMF 250 may provide a package of end-user functions with theresponsibility for the management of a network, which may includenetwork elements with VNFs 208, non-virtualized network functions, orboth (management of the VNFs 208 may occur via the NFMF 260). The OSSportion of the OSS/BSS 222 is responsible for network management, faultmanagement, configuration management and service management. The BSSportion of the OSS/BSS 222 is responsible for customer management,product management and order management. In the NFV architecture, thecurrent BSS/OSS 222 of an operator may be interworking with an NFVmanagement and orchestration (NFV-MANO) 232 using standard interfaces(or reference points).

Interconnection points (or reference points) between functional blockscan expose an external view of a functional block. These can includeOS-Ma-nfvo between the NMF 250 and NFVO 212; Ve-VNFM-em between the NFMF260 and the VNFM 206; Ve-Vnfm-vnf between a VNF 208 and VNFM 206;Or-Vnfm between the NFVO 212 and the VNFM 206; Or-Vi between the NFVO212 and the VIM 202; Vi-Vnfm between the VNFM 206 and VIM 202; NF-Vibetween the NFVI 204 and the VIM 202; and VN-Nf between the NFVI 204 andVNF 208.

A virtualized resource performance management interface has been definedfor reference point Vi-Vnfm between VIM 202 and VNFM 206 as shown inFIG. 2B. The operations to create a PM job and notify the availabilityof PM data can be transmitted using the above-mentioned interface. Theusage of an individual virtual CPU (sometimes called a virtual processoror vCPU) is a part of a virtualized resource (VR), or the consolidatedusage of all virtual CPUs of a Virtualized Compute Resource and can bemonitored by a performance measurement.

The following embodiments describe example life cycle management usecases and configuration management use cases. In these use cases,certain example compliance rules may designate qualifiers for certainsteps, such as mandatory (M), optional (0), and/or conditional (C).These qualifiers are provided by way of example only and not to limitthe disclosure.

Life Cycle Management Use Cases

FIG. 3 is a flow chart of a method 300 to instantiate a NS according tocertain embodiments. As discussed below with respect to TABLES 1-3, themethod 300 may be used by an NMF in cooperation with an NFVO to, forexample, (a) instantiate a NS containing a new VNF that is part of agNB, (b) to instantiate a NS containing a PNF that is part of a gNB, or(c) to instantiate a NS containing a PNF and a new VNF that form a gNB.

The method 300 begins 312 when the NMF decides to instantiate a NS.Then, the NMF requests 314 the NFVO to create a new NS identifier. See,e.g., clause 7.3.2 of ETSI GS NFV-IFA013 “Network FunctionVirtualization (NFV); Management and Orchestration; Os-Ma-nfvo ReferencePoint—Interface and Information Model Specification” (hereinafter, “GSNFV-IFA013”). A create NS identifier operation used in certainembodiments creates a NS instance identifier, and an associated instanceof a Nslnfo information element identified by that identifier, in aNOT_INSTANTIATED state without instantiating the NS or doing anyadditional lifecycle operation(s). The operation may allow an immediatereturn of a NS instance identifier that can be used in subsequentlifecycle operations.

The NFVO creates 316 a new Nslnfo object and returns the NS instanceidentifier to the NMF. See, clause 7.3.2.4 of GS NFV-IFA013. In case ofsuccess, a NS instance identifier and the associated instance of aNslnfo information element has been created in the NOT_INSTANTIATEDstate and can be used in subsequent lifecycle operations. In case offailure, appropriate error information is returned.

The NMF sends 318 a request to the NFVO to instantiate the NS, asdescribed in more detail with respect to TABLES 1-3. In certainembodiments, the NMF may invoke the instantiate NS operation. See, e.g.,clause 7.3.3 of GS NFV-IFA013. The instantiate NS operation allows forreferences to existing VNF instances and NS instances that are to beused in the new NS (i.e., the NS being instantiated) and additionalparameterization for new VNFs and NSs. A hierarchy of nested NS and VNFsbelow the NS being instantiated may be acyclic (i.e., no loops). AvnfProfile information element in a network service descriptor (NSD)allows the OSS/BSS to specify the number of VNFs to be created at NSinstantiation time (it is possible for this number to be zero). A NSDinstance, which can be reused among different NS instantiations, isindicated using the create NS operation previous to executing theinstantiate NS operation.

The NFVO responds 320 to the NMF with the operation result containingthe lifecycle operation occurrence identifier (Id), the NFVO sends 322the NS lifecycle change notification to the NMF indicating the start ofthe NS instantiation procedure, and the NFVO sends 324 the NS lifecyclechange notification to NMF indicating the result of NS instantiation.See, e.g., clause 7.3.3.4 of GS NFV-IFA013. In case of success, the NShas been instantiated and in case of failure appropriate errorinformation is provided in a “result” lifecycle change notification. Incertain embodiments, the NFVO first returns alifecycleOperationOccurrence Id and second sends a “start” lifecyclechange notification before additional notifications or messages as partof the operation are issued or operations towards the VNFM or VIM areinvoked. On the successful completion of the operation, the NFVO sendsthe “result” lifecycle change notification (e.g., indicating the NS hasbeen instantiated). If the NS instance was already in the INSTANTIATEDstate, the operation fails. The method 300 ends 326 when the NMFreceives the notification from the NFVO indicating the NS has beeninstantiated.

TABLE 1 shows an example life cycle management use case, which may beused with the method 300 shown in FIG. 3, for instantiation of NScontaining new VNF that is part of a gNB according to one embodiment.

TABLE 1 Use Case Stage Evolution/Specification Goal Enable NMF toinstantiate a NS that contains a new VNF (CU) that is part of a gNB viaOs-Ma-nfvo reference point. Actors/Roles NMF Telecom NMF, NFVO resourcesAssumptions Part of a gNB (CU) can be deployed as VNF. PNF part of a gNBis not yet available at the time of NS instantiation. Pre- The VNFPackage for the VNF instantiation is on-boarded conditions and enabled.Begins when NMF decides to instantiate a NS that contains a new VNF thatis part of a gNB. Step 1 (M) NMF requests NFVO to create a new NSidentifier. Step 2 (M) NFVO creates a new NsInfo object and returns theNS instance identifier to the NMF. Step 3 (M) NMF sends a request toNFVO to instantiate a NS including instantiating a new VNF instance thatis part of gNB with the following parameter: additionalParamForVnf,which provides additional parameter(s) per VNF instance. Step 4 (M) NFVOresponds to NMF with the operation result containing the lifecycleoperation occurrence Id. Step 5 (M) NFVO sends the NS lifecycle changenotification to NMF indicating the start of NS instantiation procedure.Step 6 (M) NFVO sends the NS Lifecycle Change notification to NMFindicating the result of NS instantiation. Ends when Ends when NMFreceives the notification from NFVO indicating the NS has beeninstantiated. Exceptions One of the steps identified above fails. Post-A new NS that contains a new VNF instance that is part conditions of gNBhas been instantiated. Traceability REQ-VRAN_Mgmt-Os-Ma-nfvo_CON-1,REQ-VRAN_Mgmt-Os-Ma-nfvo_CON-4

The method 300 of FIG. 3 and TABLE 1 enables an NMF to instantiate a NSthat includes a new VNF (CU or upper layer of NR BS) that is part of agNB via the Os-Ma-nfvo reference point (see, e.g., FIGS. 2A and 2B). Inthis example, it is assumed that part of the gNB (CU or upper layer ofNR BS) can be deployed as the VNF, and that the PNF part of the gNB isnot yet available at the time of the NS instantiation. This example alsosets as a pre-condition that a VNF package for the VNF instantiation ison-boarded and enabled.

With reference to the method 300 of FIG. 3 and TABLE 1, the method 300begins 312 when the NMF decides to instantiate a NS that contains thenew VNF that is part of a gNB. The NMF requests 314 the NFVO to create anew NS identifier. The new NS identifier may be based on a NSD thatreferences to one or more virtualized network function (VNF) descriptorsof virtualized parts of a base station and/or one or more physicalnetwork function (PNF) descriptors of non-virtualized parts of the basestation. The NFVO creates 316 a new Nslnfo object and returns the NSinstance identifier to the NMF. Then, the NMF sends 318 a request to theNFVO to instantiate a NS including instantiating a new VNF instance thatis part of gNB with the following parameter: additionalParamForVnf,which provides additional parameter(s) per VNF instance. The method 300proceeds as described above with respect to FIGS. 3 (at 320, 322, 324,and 326). Exceptions may be handled when one of the identified stepsfails. The method 300 results in an instantiated new NS that contains anew VNF instance that is part of a gNB.

TABLE 2 shows an example life cycle management use case, which may beused with the method 300 shown in FIG. 3, for instantiation of NScontaining PNF that is part of a gNB.

TABLE 2 Use Case Stage Evolution/Specification Goal Enable NMF toinstantiate a NS that contains PNF (DU) that is part of a gNB viaOs-Ma-nfvo reference point. Actors and NMF Roles Telecom NMF, NFVOresources Assumptions PNF part of a gNB has been deployed. Pre-conditions Begins when NMF decides to instantiate a NS that contains PNFthat is part of a gNB. Step 1 (M) NMF requests NFVO to create a new NSidentifier. Step 2 (M) NFVO creates a new NsInfo object and returns theNS instance identifier to the NMF. Step 3 (M) NMF sends a request toNFVO to instantiate a NS that contains PNF, with the followingparameter: pnfInfo, which provides the information of PNF that is partof a gNB. Step 4 (M) NFVO responds to NMF with the operation resultcontaining the lifecycle operation occurrence Id. Step 5 (M) NFVO sendsthe NS lifecycle change notification to NMF indicating the start of NSinstantiation procedure. Step 6 (M) NFVO sends the NS Lifecycle Changenotification to NMF indicating the result of NS instantiation. Ends whenEnds when NMF receives the notification from NFVO indicating the NS hasbeen instantiated. Exceptions One of the steps identified above fails.Post- A new NS that contains PNF and new VNF that form a conditions gNBhas been instantiated. Traceability REQ-VRAN_Mgmt-Os-Ma-nfvo_CON-2,REQ-VRAN_Mgmt-Os-Ma-nfvo_CON-4

The method 300 of FIG. 3 and TABLE 2 enables an NMF to instantiate a NSthat contains PNF (DU or lower layer of NR BS) that is part of a gNB viathe Os-Ma-nfvo reference point (see, e.g., FIGS. 2A and 2B). In thisexample, it is assumed that the PNF part of the gNB has been deployed.

With reference to the method 300 of FIG. 3 and TABLE 2, the method 300begins 312 when the NMF decides to instantiate a NS that contains a PNFthat is part of a gNB. The NMF requests 314 the NFVO to create a new NSidentifier, and the NFVO creates 316 a new Nslnfo object and returns theNS instance identifier to the NMF. Then, the NMF sends 318 a request tothe NFVO to instantiate a NS that contains PNF, with the followingparameter: pnflnfo, which provides the information of PNF that is partof a gNB. The method 300 proceeds as described above with respect toFIGS. 3 (at 320, 322, 324, and 326). Exceptions may be handled when oneof the identified steps fails. The method 300 results in an instantiatednew NS that contains a PNF and a new VNF that form a gNB.

TABLE 3 shows an example life cycle management use case, which may beused with the method 300 shown in FIG. 3, for instantiation of NScontaining PNF and new VNF that form a gNB.

TABLE 3 Use Case Stage Evolution/Specification Goal Enable NMF toinstantiate a NS that contains PNF (DU) and new VNF (CU) via Os-Ma-nfvoreference point. Actors and NMF Roles Telecom NMF, NFVO resourcesAssumptions Part of a gNB (CU) can be deployed as VNF. PNF part of a gNBhas been deployed. Pre- VNF Package for VNF instantiation is on-boardedand conditions enabled. Begins when NMF decides to instantiate a NS thatcontains PNF and a new VNF that form a gNB. Step 1 (M) NMF requests NFVOto create a new NS identifier. Step 2 (M) NFVO creates a new NsInfoobject and returns the NS instance identifier to the NMF. Step 3 (M) NMFsends a request to NFVO to instantiate a NS that contains PNF and newVNF, with the following parameters: additionalParamForVnf, whichprovides additional parameter(s) per VNF instance; and pnfInfo, whichprovides the information of PNF that is part of a gNB. Step 4 (M) NFVOresponds to NMF with the operation result containing the lifecycleoperation occurrence Id. Step 5 (M) NFVO sends the NS lifecycle changenotification to NMF indicating the start of NS instantiation procedure(see clause 7.3.3.4 of ETSI GS NFV-IFA 013 [2]). Step 6 (M) NFVO sendsthe NS Lifecycle Change notification to NMF indicating the result of NSinstantiation. Ends when Ends when NMF receives the notification fromNFVO indicating the NS has been instantiated. Exceptions One of thesteps identified above fails. Post- A new NS that contains PNF and a newVNF that form a conditions gNB has been instantiated. TraceabilityREQ-VRAN_Mgmt-Os-Ma-nfvo_CON-3, REQ-VRAN_Mgmt-Os-Ma-nfvo_CON-4

The method 300 of FIG. 3 and TABLE 3 enables an NMF to instantiate a NSthat contains PNF (DU or lower layer of NR BS) and new VNF (CU or upperlayer of NR BS) via the Os-Ma-nfvo reference point (see, e.g., FIGS. 2Aand 2B). In this example, it is assumed that part of a gNB (CU or upperlayer of NR BS) can be deployed as VNF, and that the PNF part of the gNBhas been deployed. This example also sets as a pre-condition that a VNFpackage for VNF instantiation is on-boarded and enabled.

With reference to the method 300 of FIG. 3 and TABLE 3, the method 300begins 312 when the NMF decides to instantiate a NS that contains PNFand a new VNF that form a gNB. The NMF requests 314 the NFVO to create anew NS identifier, and the NFVO creates 316 a new Nslnfo object andreturns the NS instance identifier to the NMF. Then, the NMF sends 318 arequest to the NFVO to instantiate a NS that contains PNF and new VNF,with the following parameters: additionalParamForVnf, which providesadditional parameter(s) per VNF instance; and pnflnfo, which providesthe information of PNF that is part of a gNB. The method 300 proceeds asdescribed above with respect to FIGS. 3 (at 320, 322, 324, and 326).Exceptions may be handled when one of the identified steps fails. Themethod 300 results in an instantiated new NS that contains PNF and a newVNF that form a gNB.

FIG. 4 is a flow chart of a method 400 to update a NS according tocertain embodiments. As discussed below with respect to TABLES 4-5, themethod 400 may be used by an NMF in cooperation with an NFVO to, forexample, (a) update a NS instance to add the VNF that is part of a gNB;and (b) update a NS instance to add the PNF that is part of a gNB.

The method 400 begins 412 when the NMF decides to update a NS. Then, theNMF sends 418 a request to the NFVO to update the NS to add the PNFinstance. See, e.g., clause 7.3.5 of GS NFV-IFA013. An update NSoperation updates an NS instance and may also be used to embed VNF lifecycle management (LCM) operations in support of a fine grained NS LCMapproach.

The NFVO responds 420 to the NMF with the operation result containingthe lifecycle operation occurrence Id, the NFVO sends 422 the NSlifecycle change notification to the NMF indicating the start of the NSupdate procedure, and the NFVO sends 424 the NS lifecycle changenotification to NMF indicating the result of NS update. See, e.g.,clause 7.3.5.4 of GS NFV-IFA013. In case of success, the NS has beenupdated according to the request. In case of failure, appropriate errorinformation is provided in the “result” lifecycle change notification.In certain embodiments, the NFVO first returns alifecycleOperationOccurrenceld and second sends a “start” lifecyclechange. Notification may be before additional notifications or messagesas part of this operation are issued, or operations towards the VNFM orVIM are invoked. In certain embodiments, on successful as well asunsuccessful completion of the operation, the NFVO send the “result”lifecycle change notification (e.g., indicating the NS instance has beenupdated). The method 400 ends 426 when the NMF receives the notificationfrom the NFVO indicating that the NS has been updated.

TABLE 4 shows an example life cycle management use case, which may beused with the method 400 shown in FIG. 4, for updating a NS instance toadd the VNF that is part of a gNB according to one embodiment.

TABLE 4 Use Case Stage Evolution/Specification Goal Enable NMF to updatea NS to add the VNF (CU) via Os-Ma-nfvo reference point. Actors and NMFRoles Telecom NMF, NFVO resources Assumptions Part of a gNB (CU) can bedeployed as VNF. Pre- The NS has been instantiated, and has contained aPNF. conditions Begins when NMF decides to use NS update to add the VNFinstance to a NS that already contains a PNF in order to form a gNB.Step 1 (M) NMF sends a request to NFVO to update a NS instance to addthe VNF instance, with the following parameters: nsInstanceId, whichprovides the identifier of the NS instance where the VNF instance is tobe added; and addVnfInstance, which provides the existing VNF instanceto be added to the NS instance. Step 4 (M) NFVO responds to NMF with theoperation result containing the lifecycle operation occurrence Id (seeclause 7.3.5.4 [2]). Step 5 (M) NFVO sends the NS lifecycle changenotification to NMF indicating the start of NS update procedure (seeclause 7.3.5.4 of ETSI GS NFV-IFA 013 [2]). Step 6 (M) NFVO sends the NSLifecycle Change notification to NMF indicating the result of NS update(see clause 7.3.5.4 of ETSI GS NFV-IFA 013 [2]). Ends when Ends when NMFreceives the notification from NFVO indicating the NS instance has beenupdated. Exceptions One of the steps identified above fails. Post- TheNS instance has been updated with addition of the conditions VNFinstance that is part of gNB. TraceabilityREQ-VRAN_Mgmt-Os-Ma-nfvo_CON-5

The method 400 of FIG. 4 and TABLE 4 enables an NMF to update a NS toadd the VNF (CU or upper layer of NR BS) via Os-Ma-nfvo reference point(see, e.g., FIGS. 2A and 2B). In this example, it is assumed that partof a gNB (CU or upper layer of NR BS) can be deployed as VNF. Thisexample also sets as a pre-condition that the NS has been instantiatedand has contained a PNF.

With reference to the method 400 of FIG. 4 and TABLE 4, the method 400begins 412 when the NMF decides to update the NS by invoking an NSupdate procedure to add the VNF instance to a NS that already contains aPNF in order to form a gNB. The NMF sends 418 a request to NFVO toupdate a NS instance to add the VNF instance, with the followingparameters: nslnstanceld, which provides the identifier of the NSinstance where the VNF instance is to be added; and addVnflnstance,which provides the existing VNF instance to be added to the NS instance.The method 400 then proceeds as described above with respect to FIGS. 4(at 420, 422, 424, and 426). Exceptions may be handled when one of theidentified steps fails. The method 400 results in the NS instance thathas been updated with addition of the VNF instance that is part of gNB.

TABLE 5 shows an example life cycle management use case, which may beused with the method 400 shown in FIG. 4, for updating a NS instance toadd the PNF that is part of a gNB according to one embodiment.

TABLE 5 Use Case Stage Evolution/Specification Goal Enable NMF to updatea NS to add the PNF of a gNB (DU) via Os-Ma-nfvo reference point. Actorsand NMF Roles Telecom NMF, NFVO resources Assumptions Part of a gNB (CU)can be deployed as VNF that has already been contained in an existing NSinstance. Pre- The NS has been instantiated, and has contained a VNF.conditions Begins when NMF decides to update a NS instance to add thePNF instance to a NS that already contains a VNF instance in order toform a gNB. Step 1 (M) NMF sends a request to NFVO to update a NSinstance to add the PNF instance, with the following parameters:nsInstanceId, which provides the identifier of the NS instance where thePNF instance is to be added; and pnfInfo, which provides the informationof PNF to be contained in the NS. Step 4 (M) NFVO responds to NMF withthe operation result containing the lifecycle operation occurrence Id.Step 5 (M) NFVO sends the NS lifecycle change notification to NMFindicating the start of NS update procedure. Step 6 (M) NFVO sends theNS Lifecycle Change notification to NMF indicating the result of NSupdate. Ends when Ends when NMF receives the notification from NFVOindicating the NS instance has been updated. Exceptions One of the stepsidentified above fails. Post- The NS instance has been updated withaddition of conditions PNF that is part of gNB. TraceabilityREQ-VRAN_Mgmt-Os-Ma-nfvo_CON-6

The method 400 of FIG. 4 and TABLE 5 enables an NMF to update a NS toadd the PNF of a gNB (DU or lower layer of NR BS) via Os-Ma-nfvoreference point (see, e.g., FIGS. 2A and 2B). In this example, it isassumed that part of a gNB (CU or upper layer of BS) can be deployed asVNF that has already been contained in an existing NS instance. Thisexample also sets as a pre-condition that the NS has been instantiatedand has contained a VNF.

With reference to the method 400 of FIG. 4 and TABLE 5, the method 400begins 412 when the NMF decides to update a NS instance to add PNFinstance to a NS that already contains a VNF instance in order to form agNB. The NMF sends 418 a request to NFVO to update a NS instance to addthe PNF instance, with the following parameters: nslnstanceld, whichprovides the identifier of the NS instance where the PNF instance is tobe added; and pnflnfo, which provides the information of PNF to becontained in the NS. It should be noted that the pnflnfo parameter isnot defined in clause 7.3.5.2 of GS NFV-IFA013. The method 400 thenproceeds as described above with respect to FIGS. 4 (at 420, 422, 424,and 426). Exceptions may be handled when one of the identified stepsfails. The method 400 results in the NS instance that has been updatedwith addition of PNF that is part of gNB.

Configuration Management Use Cases

FIG. 5 is a flow chart of a method 500 to establish a relation between anetwork function instance that is virtualized and network functioninstance that is non-virtualized forming a gNB according to certainembodiments. As discussed below with respect to TABLE 6, the method 500may be used by an NMF in cooperation with an NFMF, a VNF, and a PNF to,for example, enable the NMF to establish a relation between a networkfunction instance that is virtualized and a network function instance orinstance(s) that are non-virtualized forming a gNB.

The method 500 begins 512 the process to establish the relationshipbetween the network function instance that is virtualized and networkfunction instance that is non-virtualized forming the gNB, and the NMFsends 518 a request to the NFMF to establish the relationship betweenthe network function instance that is virtualized and the networkfunction instance that is non-virtualized. Then, the NFMF validates 520the relations between the network function instance that is virtualizedand network function instance(s) that are non-virtualized, and responds522 to the NMF about the result of the relation establishment. Themethod 500 ends 526 when the NMF receives the result of the relationshipestablishment.

TABLE 6 shows an example configuration management use case, which may beused with the method 500 shown in FIG. 5, for establishment of arelation between the network function instance that is virtualized andthe network function instance or instances that are non-virtualizedaccording to one embodiment.

TABLE 6 Use Case Stage Evolution/Specification Goal Enable NMF toestablish the relation between network function instance that isvirtualized and network function instance that is non-virtualizedforming a gNB. Actors and NMF Roles Telecom NMF, NFMF, VNF, PNFresources Assumptions Pre- VNF instance of a gNB has been instantiated;PNF conditions instance of a gNB has been deployed; MOIs of the networkfunction instances realized by the VNF instance and network functioninstances realized by the PNF instance forming a gNB have been created;and NMF knows which network function instance that is virtualized andnetwork function instance that is non-virtualized compose a gNB. Beginswhen NMF decides to establish the relation between a network functioninstance that is virtualized and a network function instance that isnon-virtualized that compose a gNB. Step 1 (M) NMF sends a request toNFMF to establish the relation between a network function instance thatis virtualized and a network function instance that is non-virtualized.Note: one network function instance that is virtualized may haverelation(s) with one or more network function instances that arenon-virtualized. In some embodiments, one network function instance thatis non-virtualized may have relations to multiple network functioninstances that are virtualized. Step 2 (M) NFMF validates the relationsbetween the network function instance that is virtualized and networkfunction instance(s) that are non-virtualized, if they are valid, NFMFconfigures the network function instance that is virtualized and networkfunction instance(s) that are non-virtualized to establish therelations. Step 3 (M) NFMF responds to NMF about the result of therelation establishment. Ends when Ends when NMF receives the result ofthe relation establishment. Exceptions One of the steps identified abovefails. Post- The relations between the network function instance that isconditions virtualized and network function instance(s) that are non-virtualized have been established. Traceability REQ-VRAN-Mgmt-CON-7,REQ-VRAN-Mgmt-CON-8

The method 500 of FIG. 5 and TABLE 6 enables the NMF to establish therelation between the network function instance that is virtualized andthe network function instance that is non-virtualized to form the gNB.This example sets as a pre-condition that: the VNF instance of thevirtualized part of gNB has been instantiated; the PNF instance of thenon-virtualized part of gNB has been deployed; the MOIs of the networkfunction instance that is virtualized and the network function instancethat is non-virtualized forming the gNB have been created; and the NMFknows which network function instance that is virtualized and networkfunction instance that is non-virtualized can form the gNB.

With reference to the method 500 of FIG. 5 and TABLE 6, the method 500begins 512 when the NMF decides to establish the relation between thenetwork function instance that is virtualized and the network functioninstance that is non-virtualized forming the gNB, and the NMF sends 518a request to the NFMF to establish the relation between the networkfunction instance that is virtualized and the network function instancethat is non-virtualized. The NFMF validates 520 the relations betweenthe network function instance that is virtualized and network functioninstance(s) that are non-virtualized. If the relations are valid, theNFMF configures the network function instance that is virtualized andthe network function instance(s) that are non-virtualized to establishthe relations. The NFMF responds 522 to the NMF about the result of therelation establishment, and the method 500 ends 526 when the NMFreceives the result of the relation establishment. Exceptions may behandled when one of the identified steps fails. The method 500 resultsin relations between the network function instance that is virtualizedand the network function instance(s) that are non-virtualized beingestablished.

The “Traceability” rows of TABLES 1-6 indicate potential requirements onmanagement of virtualized network functions that are part of the NR,according to certain embodiments for the Os-Ma-nfvo reference point (seeFIGS. 2A and 2B).

“REQ-VRAN_Mgmt-Os-Ma-nfvo_CON-1” indicates that the Os-Ma-nfvo referencepoint should support the capability allowing NMF to instantiate a NSincluding instantiating a new VNF instance that is part of gNB.

“REQ-VRAN_Mgmt-Os-Ma-nfvo_CON-2” indicates that the Os-Ma-nfvo referencepoint should support the capability allowing NMF to instantiate a NScontaining the PNF instance that is part of gNB.

“REQ-VRAN_Mgmt-Os-Ma-nfvo_CON-3” indicates that the Os-Ma-nfvo referencepoint should support the capability allowing NMF to instantiate a NScontaining the PNF and the new VNF that form a gNB.

“REQ-VRAN_Mgmt-Os-Ma-nfvo_CON-4” indicates that the Os-Ma-nfvo referencepoint should support the capability allowing NFVO to notify NMF aboutchanges of an NS instance that are related to NS lifecycle managementoperations (e.g., the addition/deletion/modification of VNFs and/orPNFs).

“REQ-VRAN_Mgmt-Os-Ma-nfvo_CON-5” indicates that the Os-Ma-nfvo referencepoint should support the capability allowing NMF to udpate a NS to addthe VNF that is part of gNB.

“REQ-VRAN_Mgmt-Os-Ma-nfvo_CON-6” indicates that the Os-Ma-nfvo referencepoint should support the capability allowing NMF to udpate a NS to addthe PNF that is part of gNB.

“REQ-VRAN-Mgmt-CON-7” indicates that the NFMF should support thecapability allowing NMF to know which VNF instance and PNF instance forma gNB.

“REQ-VRAN-Mgmt-CON-8” indicates that the NFMF should support thecapability allowing NMF to establish the relation between the networkfunction instance that is virtualized and the network functioninstance(s) that are non-virtualized forming a gNB.

FIG. 6 illustrates an architecture of a system 600 of a network inaccordance with some embodiments. The system 600 is shown to include auser equipment (UE) 601 and a UE 602. The UEs 601 and 602 areillustrated as smartphones (e.g., handheld touchscreen mobile computingdevices connectable to one or more cellular networks), but may alsocomprise any mobile or non-mobile computing device, such as PersonalData Assistants (PDAs), pagers, laptop computers, desktop computers,wireless handsets, or any computing device including a wirelesscommunications interface.

In some embodiments, any of the UEs 601 and 602 can comprise an Internetof Things (IoT) UE, which can comprise a network access layer designedfor low-power IoT applications utilizing short-lived UE connections. AnIoT UE can utilize technologies such as machine-to-machine (M2M) ormachine-type communications (MTC) for exchanging data with an MTC serveror device via a public land mobile network (PLMN), Proximity-BasedService (ProSe) or device-to-device (D2D) communication, sensornetworks, or IoT networks. The M2M or MTC exchange of data may be amachine-initiated exchange of data. An IoT network describesinterconnecting IoT UEs, which may include uniquely identifiableembedded computing devices (within the Internet infrastructure), withshort-lived connections. The IoT UEs may execute background applications(e.g., keep-alive messages, status updates, etc.) to facilitate theconnections of the IoT network.

The UEs 601 and 602 may be configured to connect, e.g., communicativelycouple, with a radio access network (RAN) 610. The RAN 610 may be, forexample, an Evolved Universal Mobile Telecommunications System (UMTS)Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), orsome other type of RAN. The UEs 601 and 602 utilize connections 603 and604, respectively, each of which comprises a physical communicationsinterface or layer (discussed in further detail below); in this example,the connections 603 and 604 are illustrated as an air interface toenable communicative coupling, and can be consistent with cellularcommunications protocols, such as a Global System for MobileCommunications (GSM) protocol, a code-division multiple access (CDMA)network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular(POC) protocol, a Universal Mobile Telecommunications System (UMTS)protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation(5G) protocol, a New Radio (NR) protocol, and the like.

In this embodiment, the UEs 601 and 602 may further directly exchangecommunication data via a ProSe interface 605. The ProSe interface 605may alternatively be referred to as a sidelink interface comprising oneor more logical channels, including but not limited to a PhysicalSidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel(PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a PhysicalSidelink Broadcast Channel (PSBCH).

The UE 602 is shown to be configured to access an access point (AP) 606via connection 607. The connection 607 can comprise a local wirelessconnection, such as a connection consistent with any IEEE 802.11protocol, wherein the AP 606 would comprise a wireless fidelity (WiFi®)router. In this example, the AP 606 may be connected to the Internetwithout connecting to the core network of the wireless system (describedin further detail below).

The RAN 610 can include one or more access nodes that enable theconnections 603 and 604. These access nodes (ANs) can be referred to asbase stations (BSs), NodeBs, evolved NodeBs (eNBs), next GenerationNodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations(e.g., terrestrial access points) or satellite stations providingcoverage within a geographic area (e.g., a cell). The RAN 610 mayinclude one or more RAN nodes for providing macrocells, e.g., macro RANnode 611, and one or more RAN nodes for providing femtocells orpicocells (e.g., cells having smaller coverage areas, smaller usercapacity, or higher bandwidth compared to macrocells), e.g., low power(LP) RAN node 612.

Any of the RAN nodes 611 and 612 can terminate the air interfaceprotocol and can be the first point of contact for the UEs 601 and 602.In some embodiments, any of the RAN nodes 611 and 612 can fulfillvarious logical functions for the RAN 610 including, but not limited to,radio network controller (RNC) functions such as radio bearermanagement, uplink and downlink dynamic radio resource management anddata packet scheduling, and mobility management.

In accordance with some embodiments, the UEs 601 and 602 can beconfigured to communicate using Orthogonal Frequency-DivisionMultiplexing (OFDM) communication signals with each other or with any ofthe RAN nodes 611 and 612 over a multicarrier communication channel inaccordance various communication techniques, such as, but not limitedto, an Orthogonal Frequency-Division Multiple Access (OFDMA)communication technique (e.g., for downlink communications) or a SingleCarrier Frequency Division Multiple Access (SC-FDMA) communicationtechnique (e.g., for uplink and ProSe or sidelink communications),although the scope of the embodiments is not limited in this respect.The OFDM signals can comprise a plurality of orthogonal subcarriers.

In some embodiments, a downlink resource grid can be used for downlinktransmissions from any of the RAN nodes 611 and 612 to the UEs 601 and602, while uplink transmissions can utilize similar techniques. The gridcan be a time-frequency grid, called a resource grid or time-frequencyresource grid, which is the physical resource in the downlink in eachslot. Such a time-frequency plane representation is a common practicefor OFDM systems, which makes it intuitive for radio resourceallocation. Each column and each row of the resource grid corresponds toone OFDM symbol and one OFDM subcarrier, respectively. The duration ofthe resource grid in the time domain corresponds to one slot in a radioframe. The smallest time-frequency unit in a resource grid is denoted asa resource element. Each resource grid comprises a number of resourceblocks, which describe the mapping of certain physical channels toresource elements. Each resource block comprises a collection ofresource elements; in the frequency domain, this may represent thesmallest quantity of resources that currently can be allocated. Thereare several different physical downlink channels that are conveyed usingsuch resource blocks.

The physical downlink shared channel (PDSCH) may carry user data andhigher-layer signaling to the UEs 601 and 602. The physical downlinkcontrol channel (PDCCH) may carry information about the transport formatand resource allocations related to the PDSCH channel, among otherthings. It may also inform the UEs 601 and 602 about the transportformat, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request)information related to the uplink shared channel. Typically, downlinkscheduling (assigning control and shared channel resource blocks to theUE 602 within a cell) may be performed at any of the RAN nodes 611 and612 based on channel quality information fed back from any of the UEs601 and 602. The downlink resource assignment information may be sent onthe PDCCH used for (e.g., assigned to) each of the UEs 601 and 602.

The PDCCH may use control channel elements (CCEs) to convey the controlinformation. Before being mapped to resource elements, the PDCCHcomplex-valued symbols may first be organized into quadruplets, whichmay then be permuted using a sub-block interleaver for rate matching.Each PDCCH may be transmitted using one or more of these CCEs, whereeach CCE may correspond to nine sets of four physical resource elementsknown as resource element groups (REGs). Four Quadrature Phase ShiftKeying (QPSK) symbols may be mapped to each REG. The PDCCH can betransmitted using one or more CCEs, depending on the size of thedownlink control information (DCI) and the channel condition. There canbe four or more different PDCCH formats defined in LTE with differentnumbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8).

Some embodiments may use concepts for resource allocation for controlchannel information that are an extension of the above-describedconcepts. For example, some embodiments may utilize an enhanced physicaldownlink control channel (EPDCCH) that uses PDSCH resources for controlinformation transmission. The EPDCCH may be transmitted using one ormore enhanced the control channel elements (ECCEs). Similar to above,each ECCE may correspond to nine sets of four physical resource elementsknown as enhanced resource element groups (EREGs). An ECCE may haveother numbers of EREGs in some situations.

The RAN 610 is shown to be communicatively coupled to a core network(CN) 620—via an S1 interface 613. In embodiments, the CN 620 may be anevolved packet core (EPC) network, a NextGen Packet Core (NPC) network,or some other type of CN. In this embodiment the S1 interface 613 issplit into two parts: the S1-U interface 614, which carries traffic databetween the RAN nodes 611 and 612 and a serving gateway (S-GW) 622, andan S1-mobility management entity (MME) interface 615, which is asignaling interface between the RAN nodes 611 and 612 and MMEs 621.

In this embodiment, the CN 620 comprises the MMEs 621, the S-GW 622, aPacket Data Network (PDN) Gateway (P-GW) 623, and a home subscriberserver (HSS) 624. The MMEs 621 may be similar in function to the controlplane of legacy Serving General Packet Radio Service (GPRS) SupportNodes (SGSN). The MMEs 621 may manage mobility aspects in access such asgateway selection and tracking area list management. The HSS 624 maycomprise a database for network users, including subscription-relatedinformation to support the network entities' handling of communicationsessions. The CN 620 may comprise one or several HSSs 624, depending onthe number of mobile subscribers, on the capacity of the equipment, onthe organization of the network, etc. For example, the HSS 624 canprovide support for routing/roaming, authentication, authorization,naming/addressing resolution, location dependencies, etc.

The S-GW 622 may terminate the S1 interface 613 towards the RAN 610, androutes data packets between the RAN 610 and the CN 620. In addition, theS-GW 622 may be a local mobility anchor point for inter-RAN nodehandovers and also may provide an anchor for inter-3GPP mobility. Otherresponsibilities may include lawful intercept, charging, and some policyenforcement.

The P-GW 623 may terminate an SGi interface toward a PDN. The P-GW 623may route data packets between the CN 620 (e.g., an EPC network) andexternal networks such as a network including the application server 630(alternatively referred to as application function (AF)) via an InternetProtocol (IP) interface 625. Generally, an application server 630 may bean element offering applications that use IP bearer resources with thecore network (e.g., UMTS Packet Services (PS) domain, LTE PS dataservices, etc.). In this embodiment, the P-GW 623 is shown to becommunicatively coupled to an application server 630 via an IPcommunications interface 625. The application server 630 can also beconfigured to support one or more communication services (e.g.,Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, groupcommunication sessions, social networking services, etc.) for the UEs601 and 602 via the CN 620.

The P-GW 623 may further be a node for policy enforcement and chargingdata collection. A Policy and Charging Enforcement Function (PCRF) 626is the policy and charging control element of the CN 620. In anon-roaming scenario, there may be a single PCRF in the Home Public LandMobile Network (HPLMN) associated with a UE's Internet ProtocolConnectivity Access Network (IP-CAN) session. In a roaming scenario withlocal breakout of traffic, there may be two PCRFs associated with a UE'sIP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF(V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF626 may be communicatively coupled to the application server 630 via theP-GW 623. The application server 630 may signal the PCRF 626 to indicatea new service flow and select the appropriate Quality of Service (QoS)and charging parameters. The PCRF 626 may provision this rule into aPolicy and Charging Enforcement Function (PCEF) (not shown) with theappropriate traffic flow template (TFT) and QoS class of identifier(QCI), which commences the QoS and charging as specified by theapplication server 630.

FIG. 7 illustrates example components of a device 700 in accordance withsome embodiments. In some embodiments, the device 700 may includeapplication circuitry 702, baseband circuitry 704, Radio Frequency (RF)circuitry 706, front-end module (FEM) circuitry 708, one or moreantennas 710, and power management circuitry (PMC) 712 coupled togetherat least as shown. The components of the illustrated device 700 may beincluded in a UE or a RAN node. In some embodiments, the device 700 mayinclude fewer elements (e.g., a RAN node may not utilize applicationcircuitry 702, and instead include a processor/controller to process IPdata received from an EPC). In some embodiments, the device 700 mayinclude additional elements such as, for example, memory/storage,display, camera, sensor, or input/output (I/O) interface. In otherembodiments, the components described below may be included in more thanone device (e.g., said circuitries may be separately included in morethan one device for Cloud-RAN (C-RAN) implementations).

The application circuitry 702 may include one or more applicationprocessors. For example, the application circuitry 702 may includecircuitry such as, but not limited to, one or more single-core ormulti-core processors. The processor(s) may include any combination ofgeneral-purpose processors and dedicated processors (e.g., graphicsprocessors, application processors, etc.). The processors may be coupledwith or may include memory/storage and may be configured to executeinstructions stored in the memory/storage to enable various applicationsor operating systems to run on the device 700. In some embodiments,processors of application circuitry 702 may process IP data packetsreceived from an EPC.

The baseband circuitry 704 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Thebaseband circuitry 704 may include one or more baseband processors orcontrol logic to process baseband signals received from a receive signalpath of the RF circuitry 706 and to generate baseband signals for atransmit signal path of the RF circuitry 706. Baseband processingcircuity 704 may interface with the application circuitry 702 forgeneration and processing of the baseband signals and for controllingoperations of the RF circuitry 706. For example, in some embodiments,the baseband circuitry 704 may include a third generation (3G) basebandprocessor 704A, a fourth generation (4G) baseband processor 704B, afifth generation (5G) baseband processor 704C, or other basebandprocessor(s) 704D for other existing generations, generations indevelopment or to be developed in the future (e.g., second generation(2G), sixth generation (6G), etc.). The baseband circuitry 704 (e.g.,one or more of baseband processors 704A-D) may handle various radiocontrol functions that enable communication with one or more radionetworks via the RF circuitry 706. In other embodiments, some or all ofthe functionality of baseband processors 704A-D may be included inmodules stored in the memory 704G and executed via a Central ProcessingUnit (CPU) 704E. The radio control functions may include, but are notlimited to, signal modulation/demodulation, encoding/decoding, radiofrequency shifting, etc. In some embodiments, modulation/demodulationcircuitry of the baseband circuitry 704 may include Fast-FourierTransform (FFT), precoding, or constellation mapping/demappingfunctionality. In some embodiments, encoding/decoding circuitry of thebaseband circuitry 704 may include convolution, tail-biting convolution,turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoderfunctionality. Embodiments of modulation/demodulation andencoder/decoder functionality are not limited to these examples and mayinclude other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry 704 may include one or moreaudio digital signal processor(s) (DSP) 704F. The audio DSP(s) 704F maybe include elements for compression/decompression and echo cancellationand may include other suitable processing elements in other embodiments.Components of the baseband circuitry may be suitably combined in asingle chip, a single chipset, or disposed on a same circuit board insome embodiments. In some embodiments, some or all of the constituentcomponents of the baseband circuitry 704 and the application circuitry702 may be implemented together such as, for example, on a system on achip (SOC).

In some embodiments, the baseband circuitry 704 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, the baseband circuitry 704 may supportcommunication with an evolved universal terrestrial radio access network(EUTRAN) or other wireless metropolitan area networks (WMAN), a wirelesslocal area network (WLAN), or a wireless personal area network (WPAN).Embodiments in which the baseband circuitry 704 is configured to supportradio communications of more than one wireless protocol may be referredto as multi-mode baseband circuitry.

RF circuitry 706 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 706 may include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. The RF circuitry 706 may include a receive signal path whichmay include circuitry to down-convert RF signals received from the FEMcircuitry 708 and provide baseband signals to the baseband circuitry704. RF circuitry 706 may also include a transmit signal path which mayinclude circuitry to up-convert baseband signals provided by thebaseband circuitry 704 and provide RF output signals to the FEMcircuitry 708 for transmission.

In some embodiments, the receive signal path of the RF circuitry 706 mayinclude mixer circuitry 706A, amplifier circuitry 706B and filtercircuitry 706C. In some embodiments, the transmit signal path of the RFcircuitry 706 may include filter circuitry 706C and mixer circuitry706A. RF circuitry 706 may also include synthesizer circuitry 706D forsynthesizing a frequency for use by the mixer circuitry 706A of thereceive signal path and the transmit signal path. In some embodiments,the mixer circuitry 706A of the receive signal path may be configured todown-convert RF signals received from the FEM circuitry 708 based on thesynthesized frequency provided by synthesizer circuitry 706D. Theamplifier circuitry 706B may be configured to amplify the down-convertedsignals and the filter circuitry 706C may be a low-pass filter (LPF) orband-pass filter (BPF) configured to remove unwanted signals from thedown-converted signals to generate output baseband signals. Outputbaseband signals may be provided to the baseband circuitry 704 forfurther processing. In some embodiments, the output baseband signals maybe zero-frequency baseband signals, although this is not a requirement.In some embodiments, the mixer circuitry 706A of the receive signal pathmay comprise passive mixers, although the scope of the embodiments isnot limited in this respect.

In some embodiments, the mixer circuitry 706A of the transmit signalpath may be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 706D togenerate RF output signals for the FEM circuitry 708. The basebandsignals may be provided by the baseband circuitry 704 and may befiltered by the filter circuitry 706C.

In some embodiments, the mixer circuitry 706A of the receive signal pathand the mixer circuitry 706A of the transmit signal path may include twoor more mixers and may be arranged for quadrature downconversion andupconversion, respectively. In some embodiments, the mixer circuitry706A of the receive signal path and the mixer circuitry 706A of thetransmit signal path may include two or more mixers and may be arrangedfor image rejection (e.g., Hartley image rejection). In someembodiments, the mixer circuitry 706A of the receive signal path and themixer circuitry 706A may be arranged for direct downconversion anddirect upconversion, respectively. In some embodiments, the mixercircuitry 706A of the receive signal path and the mixer circuitry 706Aof the transmit signal path may be configured for super-heterodyneoperation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, the RFcircuitry 706 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry and the baseband circuitry704 may include a digital baseband interface to communicate with the RFcircuitry 706.

In some dual-mode embodiments, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 706D may be afractional-N synthesizer or a fractional N/N+1 synthesizer, although thescope of the embodiments is not limited in this respect as other typesof frequency synthesizers may be suitable. For example, synthesizercircuitry 706D may be a delta-sigma synthesizer, a frequency multiplier,or a synthesizer comprising a phase-locked loop with a frequencydivider.

The synthesizer circuitry 706D may be configured to synthesize an outputfrequency for use by the mixer circuitry 706A of the RF circuitry 706based on a frequency input and a divider control input. In someembodiments, the synthesizer circuitry 706D may be a fractional N/N+1synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either the baseband circuitry 704 orthe application circuitry 702 (such as an applications processor)depending on the desired output frequency. In some embodiments, adivider control input (e.g., N) may be determined from a look-up tablebased on a channel indicated by the application circuitry 702.

Synthesizer circuitry 706D of the RF circuitry 706 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some embodiments, the divider may be a dual modulusdivider (DMD) and the phase accumulator may be a digital phaseaccumulator (DPA). In some embodiments, the DMD may be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some example embodiments, theDLL may include a set of cascaded, tunable, delay elements, a phasedetector, a charge pump and a D-type flip-flop. In these embodiments,the delay elements may be configured to break a VCO period up into Ndequal packets of phase, where Nd is the number of delay elements in thedelay line. In this way, the DLL provides negative feedback to helpensure that the total delay through the delay line is one VCO cycle.

In some embodiments, the synthesizer circuitry 706D may be configured togenerate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In someembodiments, the output frequency may be a LO frequency (fLO). In someembodiments, the RF circuitry 706 may include an IQ/polar converter.

FEM circuitry 708 may include a receive signal path which may includecircuitry configured to operate on RF signals received from one or moreantennas 710, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 706 for furtherprocessing. The FEM circuitry 708 may also include a transmit signalpath which may include circuitry configured to amplify signals fortransmission provided by the RF circuitry 706 for transmission by one ormore of the one or more antennas 710. In various embodiments, theamplification through the transmit or receive signal paths may be donesolely in the RF circuitry 706, solely in the FEM circuitry 708, or inboth the RF circuitry 706 and the FEM circuitry 708.

In some embodiments, the FEM circuitry 708 may include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry 708 may include a receive signal path and a transmit signalpath. The receive signal path of the FEM circuitry 708 may include anLNA to amplify received RF signals and provide the amplified received RFsignals as an output (e.g., to the RF circuitry 706). The transmitsignal path of the FEM circuitry 708 may include a power amplifier (PA)to amplify input RF signals (e.g., provided by the RF circuitry 706),and one or more filters to generate RF signals for subsequenttransmission (e.g., by one or more of the one or more antennas 710).

In some embodiments, the PMC 712 may manage power provided to thebaseband circuitry 704. In particular, the PMC 712 may controlpower-source selection, voltage scaling, battery charging, or DC-to-DCconversion. The PMC 712 may often be included when the device 700 iscapable of being powered by a battery, for example, when the device 700is included in a UE. The PMC 712 may increase the power conversionefficiency while providing desirable implementation size and heatdissipation characteristics.

FIG. 7 shows the PMC 712 coupled only with the baseband circuitry 704.However, in other embodiments, the PMC 712 may be additionally oralternatively coupled with, and perform similar power managementoperations for, other components such as, but not limited to, theapplication circuitry 702, the RF circuitry 706, or the FEM circuitry708.

In some embodiments, the PMC 712 may control, or otherwise be part of,various power saving mechanisms of the device 700. For example, if thedevice 700 is in an RRC_Connected state, where it is still connected tothe RAN node as it expects to receive traffic shortly, then it may entera state known as Discontinuous Reception Mode (DRX) after a period ofinactivity. During this state, the device 700 may power down for briefintervals of time and thus save power.

If there is no data traffic activity for an extended period of time,then the device 700 may transition off to an RRC_Idle state, where itdisconnects from the network and does not perform operations such aschannel quality feedback, handover, etc. The device 700 goes into a verylow power state and it performs paging where again it periodically wakesup to listen to the network and then powers down again. The device 700may not receive data in this state, and in order to receive data, ittransitions back to an RRC_Connected state.

An additional power saving mode may allow a device to be unavailable tothe network for periods longer than a paging interval (ranging fromseconds to a few hours). During this time, the device is totallyunreachable to the network and may power down completely. Any data sentduring this time incurs a large delay and it is assumed the delay isacceptable.

Processors of the application circuitry 702 and processors of thebaseband circuitry 704 may be used to execute elements of one or moreinstances of a protocol stack. For example, processors of the basebandcircuitry 704, alone or in combination, may be used to execute Layer 3,Layer 2, or Layer 1 functionality, while processors of the applicationcircuitry 702 may utilize data (e.g., packet data) received from theselayers and further execute Layer 4 functionality (e.g., transmissioncommunication protocol (TCP) and user datagram protocol (UDP) layers).As referred to herein, Layer 3 may comprise a radio resource control(RRC) layer, described in further detail below. As referred to herein,Layer 2 may comprise a medium access control (MAC) layer, a radio linkcontrol (RLC) layer, and a packet data convergence protocol (PDCP)layer, described in further detail below. As referred to herein, Layer 1may comprise a physical (PHY) layer of a UE/RAN node, described infurther detail below.

FIG. 8 illustrates example interfaces of baseband circuitry inaccordance with some embodiments. As discussed above, the basebandcircuitry 704 of FIG. 7 may comprise processors 704A-704E and a memory704G utilized by said processors. Each of the processors 704A-704E mayinclude a memory interface, 804A-804E, respectively, to send/receivedata to/from the memory 704G.

The baseband circuitry 704 may further include one or more interfaces tocommunicatively couple to other circuitries/devices, such as a memoryinterface 812 (e.g., an interface to send/receive data to/from memoryexternal to the baseband circuitry 704), an application circuitryinterface 814 (e.g., an interface to send/receive data to/from theapplication circuitry 702 of FIG. 7), an RF circuitry interface 816(e.g., an interface to send/receive data to/from RF circuitry 706 ofFIG. 7), a wireless hardware connectivity interface 818 (e.g., aninterface to send/receive data to/from Near Field Communication (NFC)components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi®components, and other communication components), and a power managementinterface 820 (e.g., an interface to send/receive power or controlsignals to/from the PMC 712.

FIG. 9 illustrates components of a core network in accordance with someembodiments. The components of the CN 620 may be implemented in onephysical node or separate physical nodes including components to readand execute instructions from a machine-readable or computer-readablemedium (e.g., a non-transitory machine-readable storage medium). In someembodiments, Network Functions Virtualization (NFV) is utilized tovirtualize any or all of the above described network node functions viaexecutable instructions stored in one or more computer readable storagemediums (described in further detail below). A logical instantiation ofthe CN 620 may be referred to as a network slice 901. A logicalinstantiation of a portion of the CN 620 may be referred to as a networksub-slice 902 (e.g., the network sub-slice 902 is shown to include thePGW 623 and the PCRF 626).

NFV architectures and infrastructures may be used to virtualize one ormore network functions, alternatively performed by proprietary hardware,onto physical resources comprising a combination of industry-standardserver hardware, storage hardware, or switches. In other words, NFVsystems can be used to execute virtual or reconfigurable implementationsof one or more EPC components/functions.

FIG. 10 is a block diagram illustrating components, according to someexample embodiments, able to read instructions from a machine-readableor computer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein. Specifically, FIG. 10 shows a diagrammaticrepresentation of hardware resources 1000 including one or moreprocessors (or processor cores) 1010, one or more memory/storage devices1020, and one or more communication resources 1030, each of which may becommunicatively coupled via a bus 1040. For embodiments where nodevirtualization (e.g., NFV) is utilized, a hypervisor 1002 may beexecuted to provide an execution environment for one or more networkslices/sub-slices to utilize the hardware resources 1000.

The processors 1010 (e.g., a central processing unit (CPU), a reducedinstruction set computing (RISC) processor, a complex instruction setcomputing (CISC) processor, a graphics processing unit (GPU), a digitalsignal processor (DSP) such as a baseband processor, an applicationspecific integrated circuit (ASIC), a radio-frequency integrated circuit(RFIC), another processor, or any suitable combination thereof) mayinclude, for example, a processor 1012 and a processor 1014.

The memory/storage devices 1020 may include main memory, disk storage,or any suitable combination thereof. The memory/storage devices 1020 mayinclude, but are not limited to any type of volatile or non-volatilememory such as dynamic random access memory (DRAM), static random-accessmemory (SRAM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), Flashmemory, solid-state storage, etc.

The communication resources 1030 may include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 1004 or one or more databases 1006 via anetwork 1008. For example, the communication resources 1030 may includewired communication components (e.g., for coupling via a UniversalSerial Bus (USB)), cellular communication components, NFC components,Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components,and other communication components.

Instructions 1050 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 1010 to perform any one or more of the methodologiesdiscussed herein. The instructions 1050 may reside, completely orpartially, within at least one of the processors 1010 (e.g., within theprocessor's cache memory), the memory/storage devices 1020, or anysuitable combination thereof. Furthermore, any portion of theinstructions 1050 may be transferred to the hardware resources 1000 fromany combination of the peripheral devices 1004 or the databases 1006.Accordingly, the memory of processors 1010, the memory/storage devices1020, the peripheral devices 1004, and the databases 1006 are examplesof computer-readable and machine-readable media.

Embodiments and implementations of the systems and methods describedherein may include various operations, which may be embodied inmachine-executable instructions to be executed by a computer system. Acomputer system may include one or more general-purpose orspecial-purpose computers (or other electronic devices). The computersystem may include hardware components that include specific logic forperforming the operations or may include a combination of hardware,software, and/or firmware.

Computer systems and the computers in a computer system may be connectedvia a network. Suitable networks for configuration and/or use asdescribed herein include one or more local area networks, wide areanetworks, metropolitan area networks, and/or Internet or IP networks,such as the World Wide Web, a private Internet, a secure Internet, avalue-added network, a virtual private network, an extranet, anintranet, or even stand-alone machines which communicate with othermachines by physical transport of media. In particular, a suitablenetwork may be formed from parts or entireties of two or more othernetworks, including networks using disparate hardware and networkcommunication technologies.

One suitable network includes a server and one or more clients; othersuitable networks may contain other combinations of servers, clients,and/or peer-to-peer nodes, and a given computer system may function bothas a client and as a server. Each network includes at least twocomputers or computer systems, such as the server and/or clients. Acomputer system may include a workstation, laptop computer,disconnectable mobile computer, server, mainframe, cluster, so-called“network computer” or “thin client,” tablet, smart phone, personaldigital assistant or other hand-held computing device, “smart” consumerelectronics device or appliance, medical device, or a combinationthereof.

Suitable networks may include communications or networking software,such as the software available from Novell®, Microsoft®, and othervendors, and may operate using TCP/IP, SPX, IPX, and other protocolsover twisted pair, coaxial, or optical fiber cables, telephone lines,radio waves, satellites, microwave relays, modulated AC power lines,physical media transfer, and/or other data transmission “wires” known tothose of skill in the art. The network may encompass smaller networksand/or be connectable to other networks through a gateway or similarmechanism.

Various techniques, or certain aspects or portions thereof, may take theform of program code (i.e., instructions) embodied in tangible media,such as floppy diskettes, CD-ROMs, hard drives, magnetic or opticalcards, solid-state memory devices, a nontransitory computer-readablestorage medium, or any other machine-readable storage medium wherein,when the program code is loaded into and executed by a machine, such asa computer, the machine becomes an apparatus for practicing the varioustechniques. In the case of program code execution on programmablecomputers, the computing device may include a processor, a storagemedium readable by the processor (including volatile and nonvolatilememory and/or storage elements), at least one input device, and at leastone output device. The volatile and nonvolatile memory and/or storageelements may be a RAM, an EPROM, a flash drive, an optical drive, amagnetic hard drive, or other medium for storing electronic data. TheeNB (or other base station) and UE (or other mobile station) may alsoinclude a transceiver component, a counter component, a processingcomponent, and/or a clock component or timer component. One or moreprograms that may implement or utilize the various techniques describedherein may use an application programming interface (API), reusablecontrols, and the like. Such programs may be implemented in a high-levelprocedural or an object-oriented programming language to communicatewith a computer system. However, the program(s) may be implemented inassembly or machine language, if desired. In any case, the language maybe a compiled or interpreted language, and combined with hardwareimplementations.

Each computer system includes one or more processors and/or memory;computer systems may also include various input devices and/or outputdevices. The processor may include a general purpose device, such as anIntel®, AMD®, or other “off-the-shelf” microprocessor. The processor mayinclude a special purpose processing device, such as ASIC, SoC, SiP,FPGA, PAL, PLA, FPLA, PLD, or other customized or programmable device.The memory may include static RAM, dynamic RAM, flash memory, one ormore flip-flops, ROM, CD-ROM, DVD, disk, tape, or magnetic, optical, orother computer storage medium. The input device(s) may include akeyboard, mouse, touch screen, light pen, tablet, microphone, sensor, orother hardware with accompanying firmware and/or software. The outputdevice(s) may include a monitor or other display, printer, speech ortext synthesizer, switch, signal line, or other hardware withaccompanying firmware and/or software.

It should be understood that many of the functional units described inthis specification may be implemented as one or more components, whichis a term used to more particularly emphasize their implementationindependence. For example, a component may be implemented as a hardwarecircuit comprising custom very large scale integration (VLSI) circuitsor gate arrays, or off-the-shelf semiconductors such as logic chips,transistors, or other discrete components. A component may also beimplemented in programmable hardware devices such as field programmablegate arrays, programmable array logic, programmable logic devices, orthe like.

Components may also be implemented in software for execution by varioustypes of processors. An identified component of executable code may, forinstance, comprise one or more physical or logical blocks of computerinstructions, which may, for instance, be organized as an object, aprocedure, or a function. Nevertheless, the executables of an identifiedcomponent need not be physically located together, but may comprisedisparate instructions stored in different locations that, when joinedlogically together, comprise the component and achieve the statedpurpose for the component.

Indeed, a component of executable code may be a single instruction, ormany instructions, and may even be distributed over several differentcode segments, among different programs, and across several memorydevices. Similarly, operational data may be identified and illustratedherein within components, and may be embodied in any suitable form andorganized within any suitable type of data structure. The operationaldata may be collected as a single data set, or may be distributed overdifferent locations including over different storage devices, and mayexist, at least partially, merely as electronic signals on a system ornetwork. The components may be passive or active, including agentsoperable to perform desired functions.

Several aspects of the embodiments described will be illustrated assoftware modules or components. As used herein, a software module orcomponent may include any type of computer instruction orcomputer-executable code located within a memory device. A softwaremodule may, for instance, include one or more physical or logical blocksof computer instructions, which may be organized as a routine, program,object, component, data structure, etc., that perform one or more tasksor implement particular data types. It is appreciated that a softwaremodule may be implemented in hardware and/or firmware instead of or inaddition to software. One or more of the functional modules describedherein may be separated into sub-modules and/or combined into a singleor smaller number of modules.

In certain embodiments, a particular software module may includedisparate instructions stored in different locations of a memory device,different memory devices, or different computers, which togetherimplement the described functionality of the module. Indeed, a modulemay include a single instruction or many instructions, and may bedistributed over several different code segments, among differentprograms, and across several memory devices. Some embodiments may bepracticed in a distributed computing environment where tasks areperformed by a remote processing device linked through a communicationsnetwork. In a distributed computing environment, software modules may belocated in local and/or remote memory storage devices. In addition, databeing tied or rendered together in a database record may be resident inthe same memory device, or across several memory devices, and may belinked together in fields of a record in a database across a network.

Reference throughout this specification to “an example” means that aparticular feature, structure, or characteristic described in connectionwith the example is included in at least one embodiment. Thus,appearances of the phrase “in an example” in various places throughoutthis specification are not necessarily all referring to the sameembodiment.

As used herein, a plurality of items, structural elements, compositionalelements, and/or materials may be presented in a common list forconvenience. However, these lists should be construed as though eachmember of the list is individually identified as a separate and uniquemember. Thus, no individual member of such list should be construed as ade facto equivalent of any other member of the same list solely based onits presentation in a common group without indications to the contrary.In addition, various embodiments and examples may be referred to hereinalong with alternatives for the various components thereof. It isunderstood that such embodiments, examples, and alternatives are not tobe construed as de facto equivalents of one another, but are to beconsidered as separate and autonomous representations.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided, such asexamples of materials, frequencies, sizes, lengths, widths, shapes,etc., to provide a thorough understanding of the embodiments. Oneskilled in the relevant art will recognize, however, that theembodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, etc. In otherinstances, well-known structures, materials, or operations are not shownor described in detail to avoid obscuring aspects of embodiments.

It should be recognized that the systems described herein includedescriptions of specific embodiments. These embodiments can be combinedinto single systems, partially combined into other systems, split intomultiple systems or divided or combined in other ways. In addition, itis contemplated that parameters/attributes/aspects/etc. of oneembodiment can be used in another embodiment. Theparameters/attributes/aspects/etc. are merely described in one or moreembodiments for clarity, and it is recognized that theparameters/attributes/aspects/etc. can be combined with or substitutedfor parameters/attributes/etc. of another embodiment unless specificallydisclaimed herein.

Although the foregoing has been described in some detail for purposes ofclarity, it will be apparent that certain changes and modifications maybe made without departing from the principles thereof. It should benoted that there are many alternative ways of implementing both theprocesses and apparatuses described herein. Accordingly, the presentembodiments are to be considered illustrative and not restrictive, andthe description is not to be limited to the details given herein, butmay be modified within the scope and equivalents of the appended claims.

The following examples pertain to further embodiments.

Example 1 is an apparatus for a network management function (NMF) of amobile network that includes virtualized network functions. Theapparatus includes an interface and a processor. The interface to sendor receive, to or from a memory, a network service (NS) identifier. Theprocessor to: generate a first request for a network functionvirtualization orchestrator (NFVO) to create a new NS identifier basedon a network service descriptor (NSD) that references to one or morevirtualized network function (VNF) descriptors of virtualized parts of abase station and/or one or more physical network function (PNF)descriptors of non-virtualized parts of the base station; in response toreceipt of the new NS identifier from the NFVO, generate a secondrequest for the NFVO to instantiate a NS instance that includesinstantiation of the virtualized parts of the base station and/or thenon-virtualized parts of the base station; and process a notificationfrom the NFVO that indicates the NS instance has been instantiated.

Example 2 is the apparatus of Example 1, wherein the second request toinstantiate the NS instance corresponds to instantiation of the NScomprising a new VNF to implement a centralized unit (CU) that is partof an upper layer of the base station.

Example 3 is the apparatus of Example 1, wherein the second request toinstantiate the NS instance corresponds to instantiation of the NScomprising one or more PNFs to implement distributed units (DUs) thatare part of a lower layer of the base station.

Example 4 is the apparatus of Example 1, wherein the second request toinstantiate the NS instance corresponds to instantiation of the NScomprising one or more PNF and a new VNF to form the base station.

Example 5 is the apparatus of any of Examples 1-4, wherein the basestation comprises a next generation radio access network (NG-RAN) nodeor g Node B (gNB).

Example 6 is the apparatus of any of Examples 1-5, wherein the processoris further to: process an operation result, from the NFVO, to determinea lifecycle operation occurrence identifier corresponding to the NSinstance; process a first NS lifecycle change notification, from theNFVO, to determine a start of instantiation of the NS instance; andprocess a second NS lifecycle change notification, from the NFVO, todetermine a result of the instantiation of the NS instance.

Example 7 is the apparatus of any of Examples 1-6, wherein the NMFcomprises network management functionality within an operation supportsystem (OSS).

Example 8 is the apparatus of any of Examples 1-7, wherein the processorenables the NMF to instantiate the NS instance via an Os-Ma-nfvoreference point.

Example 9 is the apparatus of any of Examples 2 or 4, wherein the secondrequest comprises an additionalParamForVnf parameter to use for theinstantiation of the NS instance comprising the new VNF.

Example 10 is the apparatus of any of Examples 3 or 4, wherein thesecond request comprises a pnflnfo parameter to use for theinstantiation of the NS instance comprising the PNF.

Example 11 is a machine readable storage medium includingmachine-readable instructions, when executed by one or more processorsfor a network management function (NMF) of a mobile network thatincludes virtualized network functions, to: generate a request for anetwork function virtualization orchestrator (NFVO) to update a networkservice (NS) instance to add a virtualized network function (VNF)instance that realizes a virtualized part of a base station or aphysical network function (PNF) instance that realizes a non-virtualizedpart of the base station; process an operation result, from the NFVO, todetermine a lifecycle operation occurrence identifier corresponding tothe NS instance; process a first NS lifecycle change notification, fromthe NFVO, to determine a start of an NS instance update operationcorresponding to the lifecycle operation occurrence identifier; andprocess a second NS lifecycle change notification, from the NFVO, todetermine a result of the NS instance update operation.

Example 12 is the machine readable storage medium of Example 11, whereinthe request is to update the NS instance to instantiate the VNF thatrealizes a centralized unit (CU) that is part of an upper layer of anext generation radio access network (NG-RAN) node or g Node B (gNB).

Example 13 is the machine readable storage medium of Example 12, whereinthe request comprises a nslnstanceld parameter that identifies the NSinstance where the VNF instance is to be instantiated, and anaddVnflnstance parameter that provides an existing VNF instance to beadded to the NS instance.

Example 14 is the machine readable storage medium of Example 11, whereinthe request is to update the NS instance to add the PNF instance thatrealizes a distributed unit (DU) that is part of a lower layer of a nextgeneration radio access network (NG-RAN) node or g Node B (gNB).

Example 15 is the machine readable storage medium of Example 14, whereinthe request comprises a nslnstanceld parameter that identifies the NSinstance where the PNF instance is to be added, and a pnflnfo parameterthat provides information of the PNF instance to be added to the NSinstance.

Example 16 is the machine readable storage medium of any of Examples11-15, wherein the processor is further to process a notification fromthe NFVO to determine that the NS instance has been updated.

Example 17 is the machine readable storage medium of any of Examples11-16, wherein the NMF comprises network management functionality withinan operation support system (OSS).

Example 18 is the machine readable storage medium of any of Examples11-17, wherein the processor enables the NMF to update the NS instancevia an Os-Ma-nfvo reference point.

Example 19 is a method for a network function management function(NFMF), the method comprising: receiving a request from a networkmanagement function (NMF) to establish a relation between one or morenetwork function instances that are virtualized and one or more networkfunction instances that are non-virtualized; performing a validation todetermine whether the relations between the one or more network functioninstances that are virtualized and the one or more network functioninstances that are non-virtualized are valid; and responding to the NMFto indicate whether or not the relation between the one or more networkfunction instances that are virtualized and the one or more networkfunction instances that are non-virtualized has been established.

Example 20 is the method of Example 19, wherein pre-conditions ofreceiving the request or performing the validation comprise one or morevirtualized network function (VNF) instances realizing network functionsthat are virtualized have been instantiated, and a managed objectinstance (MOI) representing the one or more network function instanceshas been created.

Example 21 is the method of Example 19, wherein pre-conditions ofreceiving the request or performing the validation comprise the one ormore PNF instances realizing network functions that are non-virtualizedhave been deployed, and a managed object instance (MOI) representing theone or more network function instances has been created.

Example 22 is the method of Example 19, wherein the relation between theone or more network function instances that are virtualized and the oneor more network function instances that are non-virtualized indicatesthat the one or more network functions that are virtualized and the oneor more network functions that are non-virtualized are used to form anext generation radio access network (NG-RAN) node or g Node B (gNB).

Example 23 is the method of Example 19, wherein a single networkfunction instance that is virtualized may have relations with the one ormore network function instances that are non-virtualized.

Example 24 is the method of Example 19, wherein a single networkfunction instance that is not virtualized may have relations with theone or more network function instances that are virtualized.

Example 25 is the method of Example 19, wherein performing thevalidation to determine that the relation between the one or morenetwork function instances that are virtualized and the one or morenetwork function instances that are non-virtualized is valid indicatesthat the NMF has a prior awareness of which network function instancesthat are virtualized and which network function instances that arenon-virtualized can be used to form a next generation radio accessnetwork (NG-RAN) node or g Node B (gNB).

Example 26 is the method of Example 19, wherein if the relation betweenthe one or more network function instances that are virtualized and theone or more network function instances that are non-virtualized isvalid, the method for the NFMF further comprises: configuring the one ormore network function instances that are virtualized and the one or morenetwork function instances that are non-virtualized to establish therelation; and sending a response to the NMF indicating the relation hasbeen established.

Example 27 is the method of Example 19, wherein if the relation betweenthe one or more network function instances that are virtualized and theone or more network function instances that are non-virtualized isinvalid, the method for the NFMF further comprises sending a response tothe NMF indicating the relation cannot be established.

Example 28 is a method for a network management function (NMF) of amobile network that includes virtualized network functions, the methodcomprising: generating a first request for a network functionvirtualization orchestrator (NFVO) to create a new network service (NS)identifier based on a network service descriptor (NSD) that referencesto one or more virtualized network function (VNF) descriptors ofvirtualized parts of a base station and/or one or more physical networkfunction (PNF) descriptors of non-virtualized parts of the base station;in response to receipt of the new NS identifier from the NFVO,generating a second request for the NFVO to instantiate a NS instancethat includes instantiation of the virtualized parts of the base stationand/or the non-virtualized parts of the base station; and processing anotification from the NFVO that indicates the NS instance has beeninstantiated.

Example 29 is the method of Example 28, wherein the second request toinstantiate the NS instance corresponds to instantiation of the NScomprising a new VNF to implement a centralized unit (CU) that is partof an upper layer of the base station.

Example 30 is the method of Example 28, wherein the second request toinstantiate the NS instance corresponds to instantiation of the NScomprising one or more PNFs to implement distributed units (DUs) thatare part of a lower layer of the base station.

Example 31 is the method of Example 28, wherein the second request toinstantiate the NS instance corresponds to instantiation of the NScomprising one or more PNF and a new VNF to form the base station.

Example 32 is the method of Example 28, wherein the base stationcomprises a next generation radio access network (NG-RAN) node or g NodeB (gNB).

Example 33 is the method of Example 28, further comprising: processingan operation result, from the NFVO, to determine a lifecycle operationoccurrence identifier corresponding to the NS instance; processing afirst NS lifecycle change notification, from the NFVO, to determine astart of instantiation of the NS instance; and processing a second NSlifecycle change notification, from the NFVO, to determine a result ofthe instantiation of the NS instance.

Example 34 is the method of Example 28, wherein the NMF comprisesnetwork management functionality within an operation support system(OSS).

Example 35 is the method of Example 28, wherein the processor enablesthe NMF to instantiate the NS instance via an Os-Ma-nfvo referencepoint.

Example 36 is the method of Example 29, wherein the second requestcomprises an additionalParamForVnf parameter to use for theinstantiation of the NS instance comprising the new VNF.

Example 37 is the method of Example 30, wherein the second requestcomprises a pnflnfo parameter to use for the instantiation of the NSinstance comprising the PNF.

Example 38 is an apparatus comprising means to perform a method asexemplified in any of Examples 19-37.

Example 39 is machine-readable storage including machine-readableinstructions, when executed, to implement a method or realize anapparatus as exemplified in any of Examples 19-37.

Example 40 is a machine readable medium including code, when executed,to cause a machine to perform the method of any one of Examples 19-37.

It will be understood by those having skill in the art that many changesmay be made to the details of the above-described embodiments withoutdeparting from the underlying principles of the invention. The scope ofthe present invention should, therefore, be determined only by thefollowing claims.

1. An apparatus for a network management function (NMF) of a mobilenetwork that includes virtualized network functions, the apparatuscomprising: an interface to send or receive, to or from a memory, anetwork service (NS) identifier; and a processor to: generate a firstrequest for a network function virtualization orchestrator (NFVO) tocreate a new NS identifier based on a network service descriptor (NSD)that references to one or more virtualized network function (VNF)descriptors of virtualized parts of a base station and/or one or morephysical network function (PNF) descriptors of non-virtualized parts ofthe base station; in response to receipt of the new NS identifier fromthe NFVO, generate a second request for the NFVO to instantiate a NSinstance that includes instantiation of the virtualized parts of thebase station and/or the non-virtualized parts of the base station; andprocess a notification from the NFVO that indicates the NS instance hasbeen instantiated.
 2. The apparatus of claim 1, wherein the secondrequest to instantiate the NS instance corresponds to instantiation ofthe NS comprising a new VNF to implement a centralized unit (CU) that ispart of an upper layer of the base station.
 3. The apparatus of claim 1,wherein the second request to instantiate the NS instance corresponds toinstantiation of the NS comprising one or more PNFs to implementdistributed units (DUs) that are part of a lower layer of the basestation.
 4. The apparatus of claim 1, wherein the second request toinstantiate the NS instance corresponds to instantiation of the NScomprising one or more PNF and a new VNF to form the base station. 5.The apparatus of claim 1, wherein the base station comprises a nextgeneration radio access network (NG-RAN) node or g Node B (gNB).
 6. Theapparatus of claim 1, wherein the processor is further to: process anoperation result, from the NFVO, to determine a lifecycle operationoccurrence identifier corresponding to the NS instance; process a firstNS lifecycle change notification, from the NFVO, to determine a start ofinstantiation of the NS instance; and process a second NS lifecyclechange notification, from the NFVO, to determine a result of theinstantiation of the NS instance.
 7. The apparatus of claim 1, whereinthe NMF comprises network management functionality within an operationsupport system (OSS).
 8. The apparatus of claim 1, wherein the processorenables the NMF to instantiate the NS instance via an Os-Ma-nfvoreference point.
 9. The apparatus of claim 2, wherein the second requestcomprises an additionalParamForVnf parameter to use for theinstantiation of the NS instance comprising the new VNF.
 10. Theapparatus of claim 3, wherein the second request comprises a pnflnfoparameter to use for the instantiation of the NS instance comprising thePNF.
 11. A machine readable storage medium including machine-readableinstructions, when executed by one or more processors for a networkmanagement function (NMF) of a mobile network that includes virtualizednetwork functions, to: generate a request for a network functionvirtualization orchestrator (NFVO) to update a network service (NS)instance to add a virtualized network function (VNF) instance thatrealizes a virtualized part of a base station or a physical networkfunction (PNF) instance that realizes a non-virtualized part of the basestation; process an operation result, from the NFVO, to determine alifecycle operation occurrence identifier corresponding to the NSinstance; process a first NS lifecycle change notification, from theNFVO, to determine a start of an NS instance update operationcorresponding to the lifecycle operation occurrence identifier; andprocess a second NS lifecycle change notification, from the NFVO, todetermine a result of the NS instance update operation.
 12. The machinereadable storage medium of claim 11, wherein the request is to updatethe NS instance to instantiate the VNF that realizes a centralized unit(CU) that is part of an upper layer of a next generation radio accessnetwork (NG-RAN) node or g Node B (gNB).
 13. The machine readablestorage medium of claim 12, wherein the request comprises a nsInstanceIdparameter that identifies the NS instance where the VNF instance is tobe instantiated, and an addVnflnstance parameter that provides anexisting VNF instance to be added to the NS instance.
 14. The machinereadable storage medium of claim 11, wherein the request is to updatethe NS instance to add the PNF instance that realizes a distributed unit(DU) that is part of a lower layer of a next generation radio accessnetwork (NG-RAN) node or g Node B (gNB).
 15. The machine readablestorage medium of claim 14, wherein the request comprises a nslnstanceldparameter that identifies the NS instance where the PNF instance is tobe added, and a pnflnfo parameter that provides information of the PNFinstance to be added to the NS instance.
 16. The machine readablestorage medium of claim 11, wherein the processor is further to processa notification from the NFVO to determine that the NS instance has beenupdated.
 17. The machine readable storage medium of claim 11, whereinthe NMF comprises network management functionality within an operationsupport system (OSS).
 18. The machine readable storage medium of claim11, wherein the processor enables the NMF to update the NS instance viaan Os-Ma-nfvo reference point.
 19. A method for a network functionmanagement function (NFMF), the method comprising: receiving a requestfrom a network management function (NMF) to establish a relation betweenone or more network function instances that are virtualized and one ormore network function instances that are non-virtualized; performing avalidation to determine whether the relations between the one or morenetwork function instances that are virtualized and the one or morenetwork function instances that are non-virtualized are valid; andresponding to the NMF to indicate whether or not the relation betweenthe one or more network function instances that are virtualized and theone or more network function instances that are non-virtualized has beenestablished.
 20. The method of claim 19, wherein pre-conditions ofreceiving the request or performing the validation comprise one or morevirtualized network function (VNF) instances realizing network functionsthat are virtualized have been instantiated, and a managed objectinstance (MOI) representing the one or more network function instanceshas been created.
 21. The method of claim 19, wherein pre-conditions ofreceiving the request or performing the validation comprise the one ormore PNF instances realizing network functions that are non-virtualizedhave been deployed, and a managed object instance (MOI) representing theone or more network function instances has been created.
 22. The methodof claim 19, wherein the relation between the one or more networkfunction instances that are virtualized and the one or more networkfunction instances that are non-virtualized indicates that the one ormore network functions that are virtualized and the one or more networkfunctions that are non-virtualized are used to form a next generationradio access network (NG-RAN) node or g Node B (gNB).
 23. The method ofclaim 19, wherein a single network function instance that is virtualizedmay have relations with the one or more network function instances thatare non-virtualized.
 24. The method of claim 19, wherein a singlenetwork function instance that is not virtualized may have relationswith the one or more network function instances that are virtualized.25. The method of claim 19, wherein performing the validation todetermine that the relation between the one or more network functioninstances that are virtualized and the one or more network functioninstances that are non-virtualized is valid indicates that the NMF has aprior awareness of which network function instances that are virtualizedand which network function instances that are non-virtualized can beused to form a next generation radio access network (NG-RAN) node or gNode B (gNB).
 26. The method of claim 19, wherein if the relationbetween the one or more network function instances that are virtualizedand the one or more network function instances that are non-virtualizedis valid, the method for the NFMF further comprises: configuring the oneor more network function instances that are virtualized and the one ormore network function instances that are non-virtualized to establishthe relation; and sending a response to the NMF indicating the relationhas been established.
 27. The method of claim 19, wherein if therelation between the one or more network function instances that arevirtualized and the one or more network function instances that arenon-virtualized is invalid, the method for the NFMF further comprisessending a response to the NMF indicating the relation cannot beestablished. 28.-30. (canceled)